home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
bbs
/
pad321.zip
/
BEHAVIOR.CFG
< prev
next >
Wrap
Text File
|
1996-10-20
|
8KB
|
176 lines
// ---------------------------------------------------------------------------
// S E T T I N G S
// ---------------------------------------------------------------------------
//
// This section controls the behaviour of padlock.
//
// Boolean settings --------------------------------------------------
//
// The following settings may be set to either True or False.
//
// if num_dupes is set to True, Padlock will not call back a user
// if his/her phone number is already being used by another user.
#define num_dupes True
// Sometimes users call and enter an incorrect phone number. Sometimes
// they pick a phone number out of the blue and sometimes they enter
// the phone number of someone they don't like. Needless to say, these
// users never make it into the system, but sometimes the person whose
// phone number they entered tries to call. The following two keywords
// tell padlock to allow verifications to a duplicate number if the
// duplicate number belongs to an unregistered user. In order to do
// this, though, Padlock needs to be able to identify registered users.
// If set to "True", the following keyword tells Padlock that all
// registered users have a security level equal or greater to
// str_new_sec. If set to "False", Padlock will not use the
// user's security level to determine if the user is registered
// or not.
#define num_dupe_sec True
// The following keyword tells Padlock that all registered users
// will have all of the keys in str_new_keys enabled and all of
// the keys in str_old_keys disabled. If set to "False", Padlock
// will not attempt to use the user's keys to identify if the user
// is registered or not.
#define num_dupe_keys False
// If num_ask_password is True, then users will be asked for their
// password in addition to their code number before they are verified.
// This option is ignored if your system uses encrypted passwords.
#define num_ask_password True
// If num_ask_codeword is True, then users will be asked for a
// code number before they are verified. If you use encrypted
// passwords, you should leave this option set to True. Otherwise,
// you should have either one or both of num_ask_password and
// num_ask_codeword set to True. Setting both to False is allowed,
// but is NOT recommended.
#define num_ask_codeword True
// Each phone number extension can be associated with a city name
// in PHONE.CTL. If a user is successfully verified and their phone
// number has a city name associated with it, Padlock can optionally
// change the name of the user's city to the city name in PHONE.CTL.
// Setting num_update_city to True will cause Padlock to change the
// user's city to the name found in PHONE.CTL. If it is set to False,
// the user's city will never be modified.
#define num_update_city True
// If the following setting is set to True, Padlock will always hang
// up before returning to the BBS if an outbound call was made. This
// setting is intended for sysops who use metered phone lines where
// every outbound call costs them money.
//
// Note: Padlock will always hang up after performing a long distance
// verification, regardless of this setting. This keyword affects only
// local calls.
#define num_always_hangup False
// String settings --------------------------------------------------
//
// The following settings must be set to a string value, enclosed
// in double quotes.
// Numeric settings --------------------------------------------------
//
// The following settings must be set to a numeric value.
//
// num_attempts sets the number of times that Padlock will attempt
// to call the user back before giving up.
#define num_attempts 3
// num_delay specifies the amount of time, in seconds, to wait between
// each dial attempt.
#define num_delay 10
// ConnectTime is the time (in seconds) to wait for the modem
// to connect. This should be long enough to give the user
// a chance to answer the phone and for the modem to connect.
#define num_connect_timeout 95
// When the modem reports NO DIAL TONE, the cbv will optionally
// attempt to dial out one or more additional times. This is useful
// if another user is attempting to call the BBS while the BBS is
// attempting to perform a call back verification. Setting this to
// 0 will disable this feature.
#define num_nodial_retries 1
// num_nodial_retry_delay is the time (in seconds) that Padlock should
// wait before attempting to dial out again when the modem reports
// NO DIAL TONE. (see num_nodial_retries, above)
#define num_nodial_retry_delay 10
// num_baudrate_check_behaviour specifies the behaviour of Padlock
// if the user's baudrate is different before and after the
// verification. In other words, this controls what Padlock does
// when the user's modem connects at a different baudrate. Possible
// values are:
//
// 0 Verification success. This setting causes Padlock
// to behave exactly as it did in versions prior to
// v3.00.
// 1 Verification fail. This aborts the verification if
// the user answers at a different baud rate.
// 2 Verification success, but hangup before returning to
// BBS.
// 3 Attempt fail.
#define num_baudrate_check_behaviour 2
// Before hanging up to call a user back, Padlock will give the user
// a code word/number which they must use to get back into the system.
// The following two settings control the types of code words that
// Padlock will generate.
// num_codeword_length sets the number of characters or digits in
// the codeword.
#define num_codeword_length 6
// num_time_bonus is the amount of time (in minutes) added to the
// user's daily time limit after a successful verification. A
// value of 0 will cause the user's time limit to remain unchanged.
#define num_time_bonus 5
// Flags -------------------------------------------------------------
//
// The following settings are enabled if they are uncommented, and
// disabled if commented out.
//
// By default, Padlock uses only digits when generating the code
// word/codenumber. I've found that this avoids users getting
// confused and typing in their login password instead of the
// code number. If you want Padlock to use a code word rather
// than a code number (containing letters rather than numbers),
// uncomment the following line. If you decide to use code words,
// you should probably also change all uses of the words "code
// number" in the user displays to read "code word".
//#define flg_use_codeword
// The following is a setting I use for debugging purposes. Don't
// uncomment it. It enables the routines that write to the modem
// even when there is a local call.
//#define ALLOW_LOCAL